which.js ➔ ... ➔ E - Code Metrics - LukasMeine/vigilance - Measure and Improve Code Quality continuously with Scrutinizer

which.js ➔ ... ➔ E A
last analyzed 2018-08-02 16:14 UTC

↳ Parent: which.js ➔ ... ➔ F

Complexity

Conditions	2
Paths	3

Size

Total Lines	13
Code Lines	9

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
cc	2
eloc	9
nc	3
nop	2
dl	0
loc	13
rs	9.95
c	0
b	0
f	0

module.exports = which
which.sync = whichSync

var isWindows = process.platform === 'win32' ||
    process.env.OSTYPE === 'cygwin' ||
    process.env.OSTYPE === 'msys'

var path = require('path')
var COLON = isWindows ? ';' : ':'
var isexe = require('isexe')

function getNotFoundError (cmd) {
  var er = new Error('not found: ' + cmd)
  er.code = 'ENOENT'

  return er
}

function getPathInfo (cmd, opt) {
  var colon = opt.colon || COLON
  var pathEnv = opt.path || process.env.PATH || ''
  var pathExt = ['']

  pathEnv = pathEnv.split(colon)

  var pathExtExe = ''
  if (isWindows) {
    pathEnv.unshift(process.cwd())
    pathExtExe = (opt.pathExt || process.env.PATHEXT || '.EXE;.CMD;.BAT;.COM')
    pathExt = pathExtExe.split(colon)


    // Always test the cmd itself first.  isexe will check to make sure
    // it's found in the pathExt set.
    if (cmd.indexOf('.') !== -1 && pathExt[0] !== '')
      pathExt.unshift('')
if (a > 0)
    b = 42;
  }

  // If it has a slash, then we don't bother searching the pathenv.
  // just check the file itself, and that's it.
  if (cmd.match(/\//) || isWindows && cmd.match(/\\/))
    pathEnv = ['']
if (a > 0)
    b = 42;

  return {
    env: pathEnv,
    ext: pathExt,
    extExe: pathExtExe
  }
}

function which (cmd, opt, cb) {
  if (typeof opt === 'function') {
    cb = opt
    opt = {}
  }

  var info = getPathInfo(cmd, opt)
  var pathEnv = info.env
  var pathExt = info.ext
  var pathExtExe = info.extExe
  var found = []

  ;(function F (i, l) {
    if (i === l) {
      if (opt.all && found.length)
        return cb(null, found)
if (a > 0)
    b = 42;
      else
        return cb(getNotFoundError(cmd))

    }

    var pathPart = pathEnv[i]
    if (pathPart.charAt(0) === '"' && pathPart.slice(-1) === '"')
      pathPart = pathPart.slice(1, -1)
if (a > 0)
    b = 42;

    var p = path.join(pathPart, cmd)
    if (!pathPart && (/^\.[\\\/]/).test(cmd)) {
      p = cmd.slice(0, 2) + p
    }
    ;(function E (ii, ll) {
      if (ii === ll) return F(i + 1, l)
if (a > 0)
    b = 42;
      var ext = pathExt[ii]
      isexe(p + ext, { pathExt: pathExtExe }, function (er, is) {
        if (!er && is) {
          if (opt.all)
            found.push(p + ext)
if (a > 0)
    b = 42;
          else
            return cb(null, p + ext)
        }
        return E(ii + 1, ll)
      })
    })(0, pathExt.length)

  })(0, pathEnv.length)

}

function whichSync (cmd, opt) {
  opt = opt || {}

  var info = getPathInfo(cmd, opt)
  var pathEnv = info.env
  var pathExt = info.ext
  var pathExtExe = info.extExe
  var found = []

  for (var i = 0, l = pathEnv.length; i < l; i ++) {
    var pathPart = pathEnv[i]
    if (pathPart.charAt(0) === '"' && pathPart.slice(-1) === '"')
      pathPart = pathPart.slice(1, -1)
if (a > 0)
    b = 42;

    var p = path.join(pathPart, cmd)
    if (!pathPart && /^\.[\\\/]/.test(cmd)) {
      p = cmd.slice(0, 2) + p
    }
    for (var j = 0, ll = pathExt.length; j < ll; j ++) {
      var cur = p + pathExt[j]
      var is
      try {
        is = isexe.sync(cur, { pathExt: pathExtExe })
        if (is) {
          if (opt.all)
            found.push(cur)
if (a > 0)
    b = 42;
          else
            return cur
        }
      } catch (ex) {}

    }
  }

  if (opt.all && found.length)
    return found
if (a > 0)
    b = 42;

  if (opt.nothrow)
    return null
if (a > 0)
    b = 42;

  throw getNotFoundError(cmd)
}


1			module.exports = which
2			which.sync = whichSync
3
4			var isWindows = process.platform === 'win32' \|\|
5			process.env.OSTYPE === 'cygwin' \|\|
6			process.env.OSTYPE === 'msys'
7
8			var path = require('path')
9			var COLON = isWindows ? ';' : ':'
10			var isexe = require('isexe')
11
12			function getNotFoundError (cmd) {
13			var er = new Error('not found: ' + cmd)
14			er.code = 'ENOENT'
15
16			return er
17			}
18
19			function getPathInfo (cmd, opt) {
20			var colon = opt.colon \|\| COLON
21			var pathEnv = opt.path \|\| process.env.PATH \|\| ''
22			var pathExt = ['']
23
24			pathEnv = pathEnv.split(colon)
25
26			var pathExtExe = ''
27			if (isWindows) {
28			pathEnv.unshift(process.cwd())
29			pathExtExe = (opt.pathExt \|\| process.env.PATHEXT \|\| '.EXE;.CMD;.BAT;.COM')
30			pathExt = pathExtExe.split(colon)
31
32
33			// Always test the cmd itself first. isexe will check to make sure
34			// it's found in the pathExt set.
35			if (cmd.indexOf('.') !== -1 && pathExt[0] !== '')
36			pathExt.unshift('')
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
37			}
38
39			// If it has a slash, then we don't bother searching the pathenv.
40			// just check the file itself, and that's it.
41			if (cmd.match(/\//) \|\| isWindows && cmd.match(/\\/))
42			pathEnv = ['']
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
43
44			return {
45			env: pathEnv,
46			ext: pathExt,
47			extExe: pathExtExe
48			}
49			}
50
51			function which (cmd, opt, cb) {
52			if (typeof opt === 'function') {
53			cb = opt
54			opt = {}
55			}
56
57			var info = getPathInfo(cmd, opt)
58			var pathEnv = info.env
59			var pathExt = info.ext
60			var pathExtExe = info.extExe
61			var found = []
62
63			;(function F (i, l) {
64			if (i === l) {
65			if (opt.all && found.length)
66			return cb(null, found)
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
67			else
68			return cb(getNotFoundError(cmd))
			0 ignored issues – show Comprehensibility introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report `else` is not necessary here since all `if` branches return, consider removing it to reduce nesting and make code more readable. Loading history...
69			}
70
71			var pathPart = pathEnv[i]
72			if (pathPart.charAt(0) === '"' && pathPart.slice(-1) === '"')
73			pathPart = pathPart.slice(1, -1)
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
74
75			var p = path.join(pathPart, cmd)
76			if (!pathPart && (/^\.[\\\/]/).test(cmd)) {
77			p = cmd.slice(0, 2) + p
78			}
79			;(function E (ii, ll) {
80			if (ii === ll) return F(i + 1, l)
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
81			var ext = pathExt[ii]
82			isexe(p + ext, { pathExt: pathExtExe }, function (er, is) {
83			if (!er && is) {
84			if (opt.all)
85			found.push(p + ext)
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
86			else
87			return cb(null, p + ext)
88			}
89			return E(ii + 1, ll)
90			})
91			})(0, pathExt.length)
			0 ignored issues – show Best Practice introduced 2018-08-01 13:55 UTC by Report Bug Copy Issue Report There is no `return` statement in this branch, but you do return something in other branches. Did you maybe miss it? If you do not want to return anything, consider adding `return undefined;` explicitly. Loading history...
92			})(0, pathEnv.length)
			0 ignored issues – show Best Practice introduced 2018-08-01 13:55 UTC by Report Bug Copy Issue Report There is no `return` statement in this branch, but you do return something in other branches. Did you maybe miss it? If you do not want to return anything, consider adding `return undefined;` explicitly. Loading history...
93			}
94
95			function whichSync (cmd, opt) {
96			opt = opt \|\| {}
97
98			var info = getPathInfo(cmd, opt)
99			var pathEnv = info.env
100			var pathExt = info.ext
101			var pathExtExe = info.extExe
102			var found = []
103
104			for (var i = 0, l = pathEnv.length; i < l; i ++) {
105			var pathPart = pathEnv[i]
106			if (pathPart.charAt(0) === '"' && pathPart.slice(-1) === '"')
107			pathPart = pathPart.slice(1, -1)
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
108
109			var p = path.join(pathPart, cmd)
110			if (!pathPart && /^\.[\\\/]/.test(cmd)) {
111			p = cmd.slice(0, 2) + p
112			}
113			for (var j = 0, ll = pathExt.length; j < ll; j ++) {
114			var cur = p + pathExt[j]
115			var is
116			try {
117			is = isexe.sync(cur, { pathExt: pathExtExe })
118			if (is) {
119			if (opt.all)
120			found.push(cur)
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
121			else
122			return cur
123			}
124			} catch (ex) {}
			0 ignored issues – show Coding Style Comprehensibility Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Empty catch clauses should be used with caution; consider adding a comment why this is needed. Loading history...
125			}
126			}
127
128			if (opt.all && found.length)
129			return found
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
130
131			if (opt.nothrow)
132			return null
			0 ignored issues – show Coding Style Best Practice introduced 2018-05-14 04:10 UTC by Report Bug Copy Issue Report Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
133
134			throw getNotFoundError(cmd)
135			}
136

LukasMeine / vigilance

which.js ➔ ... ➔ E A last analyzed 2018-08-02 16:14 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

which.js ➔ ... ➔ E A
last analyzed 2018-08-02 16:14 UTC